!testme

Alrighty!

!testme

Meow 🐈

Will this patch fix the issue where BorgWarehouse does not want to create a repo because it is missing ~/.ssh/authorized_keys?

!testme

Alrighty!

Will this patch fix the issue where BorgWarehouse does not want to create a repo because it is missing ~/.ssh/authorized_keys?

This PR needs to be tested

@ericgaspar, can I help in any way?

if you are willing to test it will help 👍

If you can walk me through what I should do, happy to.

(I’m new to YunoHost, but not new to Linux)

@ericgaspar , if you release a testing version on YunoHost, I’d be glad to take it for a spin and report my experience.

You can test (install or upgrade) this branch with this commands in a terminal

sudo yunohost app install https://github.com/YunoHost-Apps/borgwarehouse_ynh/tree/path
or
sudo yunohost app upgrade borgwarehouse -u https://github.com/YunoHost-Apps/borgwarehouse_ynh/tree/path --force

Thanks, @ericgaspar ,

If I just force upgrade and restart the service, I still get this error when trying to add a repository:

An error has occurred : /home/borgwarehouse/.ssh/authorized_keys must be present

But if I remove the app and (re-)install it, it seems to work now.

OK, I am running into another problem: I can create backup repos, but cannot seem to access them.

If I try to borg init a repo from my laptop that I created using BorgWarehouse@YunoHost, I get the following error:

borgwarehouse@{$domain}'s password: Remote: Permission denied, please try again.

I have no idea which password it wants from me.

I also tried to import the repository from my old borg server, but it does not seem to show up as used space in the dashboard.

That brings me to the question where does BorgWarehouse on YunoHost expect the repos/ to be?

BTW, I don’t know if this affects anything, but even though there is /home/borgwarehouse/, borgwarehouse’s home directory is still set to /var/www/borgwarehouse/.

I tried again to init a backup repository with borg init --debug -e repokey-blake2 […] and I get:

sing builtin fallback logging configuration
33 self tests completed in 0.04 seconds
SSH command line: ['ssh', '-p', '22', '{redacted}', 'borg', 'serve', '--debug']
Remote: ssh: connect to host {redacted} port 22: Connection refused
Connection closed by remote host. Is borg working on the server?
Traceback (most recent call last):
  File "/usr/lib/python3.11/site-packages/borg/archiver.py", line 5343, in main
    exit_code = archiver.run(args)
                ^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/site-packages/borg/archiver.py", line 5263, in run
    return set_ec(func(args))
                  ^^^^^^^^^^
  File "/usr/lib/python3.11/site-packages/borg/archiver.py", line 167, in wrapper
    repository = RemoteRepository(location.omit_archive(), create=create, exclusive=argument(args, exclusive),
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/site-packages/borg/remote.py", line 578, in __init__
    raise ConnectionClosedWithHint('Is borg working on the server?') from None
borg.remote.ConnectionClosedWithHint: Connection closed by remote host. Is borg working on the server?

Platform: Linux leza 6.6.8-zen1-1-zen #1 ZEN SMP PREEMPT_DYNAMIC Thu, 21 Dec 2023 19:00:41 +0000 x86_64
Linux: Unknown Linux  
Borg: 1.2.7  Python: CPython 3.11.6 msgpack: 1.0.5 fuse: llfuse 1.5.0 [pyfuse3,llfuse]
PID: 239375  CWD: /home/hook
sys.argv: ['/usr/bin/borg', 'init', '--debug', '-e', 'repokey-blake2', 'ssh://borgwarehouse@{redacted}']
SSH_ORIGINAL_COMMAND: None

@ericgaspar , anything else I can help with?

I’m interested to getting this fixed, as migrating my Borg backups to YuNoHost is the last thing keeping my noisy old server(s) running.

I poked around a bit and it seems to be a permission (and folder location) issue.

@ericgaspar would you mind giving me the rights on this repo ?
I need to use borgwarehouse so I'll solve the issues first

!testme

May the CI gods be with you!

📚

superseded by #13 after a rebase of these commits